-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added osName to 2022-05-10-preview #19970
Conversation
Hi, @justinytchen Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
compared swaggers (via Oad v0.9.6)] | new version | base version |
---|---|---|
HybridCompute.json | 2022-05-10-preview(68ae29b) | 2022-05-10-preview(main) |
Rule | Message |
---|---|
1045 - AddedOptionalProperty |
The new version has a new optional property 'osName' that was not found in the old version. New: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L977:7 Old: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L977:7 |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-preview-2022-05 | package-preview-2022-05(68ae29b) | package-preview-2022-05(main) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1143 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1177 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1225 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1245 |
|
The child tracked resource, 'extensions' with immediate parent 'Machine', must have a list by immediate parent operation. Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1222 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L746 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableAutomaticUpgrade Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1276 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: autoUpgradeMinorVersion Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1280 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableAutomaticUpgrade Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1325 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: autoUpgradeMinorVersion Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L1329 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List Machines by resource group Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L318 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Create or Update a Machine Extension Location: Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#L450 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️⚠️
SDK Track2 Validation: 4 Warnings warning [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/68ae29be6cf760bfce8f805b1d7ba731c478f286/specification/hybridcompute/resource-manager/readme.md#tag-package-preview-2022-05">hybridcompute/resource-manager/readme.md#package-preview-2022-05
Rule | Message |
---|---|
"readme":"hybridcompute/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"The schema 'components·1pl4ixg·schemas·machineextensionproperties·properties·settings·additionalproperties' has no type or format information whatsoever. Location:\n file:///mnt/vss/_work/1/azure-rest-api-specs/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#/components/schemas/components·1pl4ixg·schemas·machineextensionproperties·properties·settings·additionalproperties" |
|
"readme":"hybridcompute/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"The schema 'components·18d558g·schemas·machineextensionproperties·properties·protectedsettings·additionalproperties' has no type or format information whatsoever. Location:\n file:///mnt/vss/_work/1/azure-rest-api-specs/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#/components/schemas/components·18d558g·schemas·machineextensionproperties·properties·protectedsettings·additionalproperties" |
|
"readme":"hybridcompute/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"The schema 'components·f9j7vk·schemas·machineextensionupdateproperties·properties·settings·additionalproperties' has no type or format information whatsoever. Location:\n file:///mnt/vss/_work/1/azure-rest-api-specs/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#/components/schemas/components·f9j7vk·schemas·machineextensionupdateproperties·properties·settings·additionalproperties" |
|
"readme":"hybridcompute/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"The schema 'components·1a7hg8v·schemas·machineextensionupdateproperties·properties·protectedsettings·additionalproperties' has no type or format information whatsoever. Location:\n file:///mnt/vss/_work/1/azure-rest-api-specs/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/preview/2022-05-10-preview/HybridCompute.json#/components/schemas/components·1a7hg8v·schemas·machineextensionupdateproperties·properties·protectedsettings·additionalproperties" |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
"readme":"hybridcompute/resource-manager/readme.md", "tag":"package-preview-2022-05", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
NewApiVersionRequired reason: |
Hi @live1206, we removed the osName field previously in this API version. It turned out that our partner teams and customers are automatically using our newest API because they don't have the control to API versions in the system they use. And this change broke their stuff. We would like to recall this change. |
To resolve the sev2 ICM sooner, I just approved this breaking change and merge the PR. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
What's the purpose of the update?
The spec for 2022-05-10-preview was unintentionally changed and the osName property was removed accidentally causing a Sev 2. This PR addresses that.
When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
As soon as possible
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
As soon as possible
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.